ci: add HOL skill-publish validate workflow#1
Open
internet-dot wants to merge 2 commits intoMrRedstoneY:mainfrom
Open
ci: add HOL skill-publish validate workflow#1internet-dot wants to merge 2 commits intoMrRedstoneY:mainfrom
internet-dot wants to merge 2 commits intoMrRedstoneY:mainfrom
Conversation
MrRedstoneY
force-pushed
the
main
branch
5 times, most recently
from
5e1f398 to
9e2bc90
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a validate-only CI check for the repo's skill metadata so metadata changes are easier to catch before they drift.
It only adds one workflow, does not publish anything, and does not touch the Django, WebSocket, or RabbitMQ runtime paths already in the repo.
I targeted this repo because it already has a structured backend surface and a small metadata-only check is easy to review in that setup.
Permissions: read-only. No secrets. No publish. No runtime changes.
If you'd rather keep it under a different workflow name or path, I can adjust the branch.